| 1. | No bounds checking is performed
不执行边界检查。 |
| 2. | Should you hand - code validation routines that perform bounds checking
您需要自己编写一些验证例程来进行边界检查么？ |
| 3. | It also performs bounds checking and eliminates indirect object access , even under error conditions
也执行数组维度检查和消除间接对象访问，甚至在错误的条件下。 |
| 4. | In some cases , unsafe code may increase an application s performance by removing array bounds checks
在某些情况下，通过移除数组界限检查，不安全代码可提高应用程序的性能。 |
| 5. | The parent class of all application settings classes , exposes four events to enable such bounds checking
是所有应用程序设置类的父类，它公开四个事件用于启用这样的界限检查。 |
| 6. | Define the event handler , and write the code inside of it to perform bounds checking on the birth date
定义事件处理程序，并在该事件处理程序中编写代码，以便对出生日期执行边界检查。 |
| 7. | A less drastic measure is to get a compiler that will perform array bounds checking for c programs . such a tool exists for gcc
这仅仅取决于您希望系统有多大的容忍度以及为获得这种容忍度您所愿意承受的性能影响。 |
| 8. | The procedures were written under the assumption that you have already created your application settings ; in this example , we will perform bounds checking on a setting named
这些过程是在假定已创建应用程序设置的情况下编写的；在此示例中，我们将对名为 |
| 9. | It s too bad that c and c don t do bounds checking automatically , but there is actually a good reason why they don t . the price of bounds checking is efficiency
有一篇论文论述了“ sitar ：用于分布式服务的可伸缩侵入容忍性（ intrusion - tolerant ）体系结构” ，其核心是两个一般性概念。 |
| 10. | One of the most significant aspects is that the combination of strict type checks , array bounds checking , and automatic garbage collection thoroughly blocks the most destructive forms of server code vulnerabilities : buffer overruns , double - release errors , and rogue pointers
最显著的方面之一是严格的类型检查、数组边界检查和自动垃圾收集的组合彻底防止了最具破坏性形式的服务器代码攻击：缓冲区溢出、重复释放的错误和游离的指针。 |
